23,797 research outputs found

    EEOC v. Sapark Enterprises, L.L.C. d/b/a Ramada Inn Pasadena

    Get PDF

    EEOC and Yolanda E. Washington and Subrena L. Tarver v. Kroger Texas, L.P.

    Get PDF

    EEOC and Charles Hickman v. Commercial Coating Services, Inc.

    Get PDF

    Programming your way out of the past: ISIS and the META Project

    Get PDF
    The ISIS distributed programming system and the META Project are described. The ISIS programming toolkit is an aid to low-level programming that makes it easy to build fault-tolerant distributed applications that exploit replication and concurrent execution. The META Project is reexamining high-level mechanisms such as the filesystem, shell language, and administration tools in distributed systems

    The ISIS project: Fault-tolerance in large distributed systems

    Get PDF
    The semi-annual status report covers activities of the ISIS project during the second half of 1989. The project had several independent objectives: (1) At the level of the ISIS Toolkit, ISIS release V2.0 was completed, containing bypass communication protocols. Performance of the system is greatly enhanced by this change, but the initial software release is limited in some respects. (2) The Meta project focused on the definition of the Lomita programming language for specifying rules that monitor sensors for conditions of interest and triggering appropriate reactions. This design was completed, and implementation of Lomita is underway on the Meta 2.0 platform. (3) The Deceit file system effort completed a prototype. It is planned to make Deceit available for use in two hospital information systems. (4) A long-haul communication subsystem project was completed and can be used as part of ISIS. This effort resulted in tools for linking ISIS systems on different LANs together over long-haul communications lines. (5) Magic Lantern, a graphical tool for building application monitoring and control interfaces, is included as part of the general ISIS releases

    Status of the Instream Flow Issue in Arkansas, 1987

    Get PDF
    Expansion of Arkansas\u27 population with concurrent increases in the state\u27s domestic, industrial, and agricultural water uses and possible out-of-state diversion are placing substantial demands on the state\u27s water resources. In an attempt to address this growing concern, Act 1051 (1985) of the Arkansas legislature was passed requiring the determination of present and future state water needs. A specific area of this mandate was the quantification of instream flow requirements. Basic instream flow needs are maintenance of the aquatic ecosystem and dependent riparian environment. Flow reservation may compliment other instream uses such as recreation, navigation, water quality, and groundwater recharge. However, offstream uses (e.g. irrigation and industry) may compete for these same flows and often at the most critical time of year. In order to answer questions concerning instream flow requirements, over 40 methods of instream flow determination have been developed, the majority in the semi-arid western United States. These individual procedures may be classified into four major methodologies: (1) discharge, (2) single transect, (3)multiple transect, and (4) regression analysis of historical data. Requirements of these four types vary according to necessary level of expertise, time and effort expended, and monetary outlay. In one year, requests for fish and wildlife instream flow needs for approximately 60 stream reaches throughout Arkansas limited the possible options. Modification and further development of a well-known method is outlined as an initial step in the process of quantifying Arkansas\u27 instream flow needs. Examples are given for some of the major river basins throughout the state
    corecore